Systems and methods for providing secure network exchanged for a multitenant virtual private cloud

ABSTRACT

Systems and methods for routing real-time voice communication via a private network exchange. A virtual private cloud (VPC) system receives first configuration for a first private network exchange for a first account of the VPC system. The VPC system assigns a first regional exchange system to the first private network exchange based on the first configuration. The first private network exchange is established between the first regional exchange system and a first outside entity system of the first account by mapping an identifier of the first account to the first private network exchange. Real-time voice communication data for the first account is routed from a first real-time voice communication service of the VPC system to the first outside entity system via the first private network exchange based on the mapping.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application Ser. No. 62/291,327, filed on 4 Feb. 2016, which is incorporated in its entirety by this reference.

TECHNICAL FIELD

This disclosure relates generally to the communication networking field, and more specifically to new and useful systems and methods for providing secure network exchange for a multitenant virtual private cloud in the communication networking field.

BACKGROUND

Many companies, products, and services use cloud-hosted computing resources during operation. Often times the cloud hosted computing resources are accessed over a public internet connection. However, use cases have legal or business restrictions or objectives that make a public internet connection not viable. In one case, the security of a connection to the cloud-hosted computing resource is not secure when established over the public internet. For example, a voice call from a customer support system may not be permitted to use public internet connections since social security or credit card numbers may be exchanged during a voice call. In another case, the quality of the connection may not be satisfactory. The bandwidth restrictions and/or the uptime of a connection through the public internet connection may not provide the level of service desired by a company. While, cloud-hosted computing resources can use network exchange solutions. There are no solutions that enable a multi-tenant platform as a service product to provide such network exchange solutions. Thus, there is a need in the communication field to create a new and useful system and method for providing a secure network exchange for a multitenant virtual cloud. This embodiments disclosed herein provide such a new and useful system and method.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a schematic representation of a system of a preferred embodiment;

FIG. 2 is a schematic representation of an exemplary configuration interface;

FIG. 3 is a flow diagram representation of a method of a preferred embodiment;

FIGS. 4A-C are schematic representations of a systems of preferred embodiments;

FIGS. 5A-D are flow diagram representations of methods of preferred embodiments;

FIG. 6 is an architecture diagram of a Virtual Private Cloud system of a preferred embodiment; and

FIG. 7 is an architecture diagram of a regional exchange system of a preferred embodiment.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following description of preferred embodiments is not intended to limit the invention to these preferred embodiments, but rather to enable any person skilled in the art to make and use this invention.

1. System

As shown in FIG. 1, a system (e.g., 100) for providing a secure network exchange for a multitenant virtual cloud of a preferred embodiment can include a set of regional exchange systems (e.g., 120, 130) that include a set of secure connection interfaces (e.g., VPN, Cross Connect, MPLS), a multitenant platform (e.g., 113) in a virtual private cloud (e.g., 110), and a configuration system (e.g., 112). The system can additionally include a virtualized IP (internet protocol) system. The system functions to enable a multitenant platform (e.g., 113) to offer network exchange functionality to a variety of entities (e.g., Customer A, Customer B, Customer C) using the multitenant platform (e.g., 113). The system is particularly applicable to a multitenant platform as a service product that is hosted in an infrastructure as a service cloud computing product such as Amazon Web Services or other suitable hosting solutions. Current exchange solutions do not address the challenge of offering network exchange capabilities to multiple entities for a platform built in a virtual private cloud (VPC) (e.g., 110). The system can be used by entities (e.g., Customer A, Customer B, Customer C) that require or desire to have a more secure or reliable data link to the multi-tenant platform (e.g., 113). For example, a company building a phone or messaging system that deals with sensitive information such as social security numbers, credit card numbers, bank account numbers, medical health records, and other sensitive information may require a network connection that is secured, where access over public internet routing is not acceptable. In another example, a company building a product that has high performance requirements relating to media quality, bandwidth, uptime, or other communication properties may find basic public internet access to be infeasible.

A set of regional exchange systems (e.g., 120, 130) functions to provide physical collocated networking infrastructure to facilitate establishing secure connections. The set of regional exchange systems (e.g., 120, 130) are preferably regionally distributed in distinct geographic locations. There may be multiple regional exchange systems in the United States and in other regions of the world. There can be any suitable geographic distance between any two regional exchange systems (e.g., 120, 130). One exemplary implementation may have over one hundred or even a thousand miles between different regional exchange systems. For example, the United States may have at least one regional exchange system based in the Western side and a second based in the Eastern side. The regional exchange systems are preferably established in collocated infrastructure environments where direct secured connections can be established to other computing resources accessible at the collocated site. Preferably, an edge computing resource is also established at the collocated site and the outside entity wanting to establish a secure connection can have a physical computing resource presence at the same collocated site. A secured connection can be made between at least one edge computing resource of the multitenant platform (e.g., 113) and a computing resource of the outside entities (e.g., Customer A, Customer B, Customer C).

Preferably, the regional exchange systems include a set of secure connection interface options that include a VPN connection, a cross connect connection, and an MPLS (Multiprotocol Label Switching) connection. The system can provide one or multiple secure connection interface options, which may include the above variations and/or any suitable alternative type of secure connection interface options. The types of secure connection interface options can be uniform in each regional exchange system but may alternatively be different for at least two subsets of regions.

A VPN (Virtual Private Network) connection interface functions to provide a straightforward and possibly faster setup time for a secure connection. The VPN can make the connection over a secured tunnel. The VPN connection interface can provide strong authentication and encrypted (e.g., IPSec) communication across the internet. The VPN can enable a secure connection while still using connectivity via the internet. The VPN connection interface can be used by an outside entity in combination with a physical or virtual router that supports IPSec VPN or other suitable internet security protocol.

A cross connect interface functions to establish a communication connection over a dedicated physical link that could be additionally encrypted. The cross connect interface can utilize a piece of circuit-switched network equipment. The cross connect interface provides a physical link to the multitenant platform, wherein the physical link is dedicated to the traffic of the outside entity. The physical link can be a fiber link, an optical link, or any suitable type of connection link. The cross connect interface can include quality of service controls. The outside entity preferably uses an established gateway presence in at least one of the collocation sites to establish a connection to the regional network exchange system through a cross connect interface. The gateway resources of the outside entity are preferably peered with the cross connect interface of the regional exchange system.

A MPLS connection interface functions to establish a connection via a private carrier network. The MPLS connection interface can be encrypted. The MPLS connection interface puts traffic of the outside entity on a separate virtual network inside a physical private network. The MPLS connection interface can provide quality of service management as part of the MPLS-based private cloud offering used by the outside entity. The MPLS connection interface offers a data-carrying service that directs data from one network node to another based on short path labels, which may avoid complex lookups in a routing table. Various access technologies may be used.

In one embodiment, the set of exchange system includes a set of customer entities leveraging a customer exchange subsystem and a set of service providers used by the multitenant platform using a service exchange subsystem. In a telecommunication platform variation, user entities such as customer care systems, business phone solutions, VoIP products, messaging services may establish secure network connections through a customer exchange subsystem, and voice and messaging carriers may establish secure network connections through a service exchange subsystem.

The multitenant platform (e.g., 113) functions to provide an operational service that involves network connections to a plurality of entities. A multitenant platform can enable multiple accounts to use the platform in facilitating various operations performed by the multitenant platform tasks. Additionally, each account within the multitenant platform may itself have a subaccount. Accordingly, an account may support multiple use-case scenarios for different sub-account holders wherein communication, data/analytics, billing, and/or other aspects can be scoped to an account, a sub-account, or any suitable scope. The multitenant platform preferably is hosted in a virtual private cloud (VPC) (e.g., 110). In other words, the multitenant platform can be built on top of third party cloud computing resources (e.g., IaaS solutions such as AWS). The multitenant platform (e.g., 113) can be a server, a server cluster, a collection of components on a distributed computing system, or any suitable network accessible computing infrastructure. The multitenant platform (e.g., 113) can be implemented in part through a service-directed architecture wherein different operational responsibilities of the platform can be subdivided between different internal services. Those services can be composed of multiple servers or machine nodes, which can preferably be scaled out horizontally and workload balanced across the set of nodes.

The multitenant platform (e.g., 113) can provide any suitable computing service. In one preferred implementation, the multitenant platform is a communication platform. The communication platform can be designed for one or more mediums of communication. The communication platform may support various forms of communication in addition to the mediums described herein. A communication platform can provide voice communication connectivity (e.g., PSTN, SIP, etc.), messaging (SMS, MMS, IP messaging, etc.), communication business logic, conferencing, broadcasting, data streaming, and/or any suitable communication operations. The communication functions to provide communication services to developer applications and services. Various outside entities can be build service and products that can leverage the functionality of the communication platform to perform one or multiple communication tasks. The system is preferably implemented in combination with a communication platform such as the one described in patent application Ser. No. 12/417,630 filed 2 Apr. 2009, entitled “System and Method for Processing Telephony Sessions”, which is hereby incorporated in its entirety by this reference. The communication platform preferably enables application execution in connection to communication sessions and/or messages; the communication platform may additionally or alternatively provide an application programming interface (API) as an alternative for interacting with communication functionality of the communication platform. Herein the multitenant platform is primarily described as being applied to the telecommunication networking space, but the platform may provide any suitable type of computing service such as financial transactions, data warehousing/processing, and/or any suitable computing service.

The multitenant platform of the system is preferably hosted in a virtual private cloud (VPC) (e.g., 110). A VPC can be an on-demand configurable pool of shared computing resources from an IaaS cloud environment. The VPC is preferably a set of resources provisioned from a third party cloud solution provider to the operator of the multitenant platform. The cloud environment generally do not provide network exchange solutions to address the needs of a multitenant platform operating within their cloud. The system in part addresses the challenges of providing a networking solution when the physical resources are provisioned by another party.

In one implementation, the computing resources within the multitenant platform are preferably operated within two subnets an edge subnet and a private subnet. A subnet is generally a block of contiguous IP addresses. Services and products can be designed so that they configure edge servers within the edge subnet and internal resources operate within the private subnet. The edge subnet includes a set of edge nodes. The edge nodes can be different services or products offered by the multitenant platform. For example, in a telecommunications platform there may be a SIP edge server, a messaging edge server, a video streaming edge server, an IP Client communication edge server, and/or any suitable type of service edge server. The edge nodes are the computing resources exposed to the outside entities connecting through the exchange system. These edge servers are preferably configured for the various services or products to talk to computing resources within the private subnet. The private subnet includes a variety of services that preferably provide the core service functionality.

A routing manager can be used to govern how the hosts in the edge subnet can reach outside entities through the network exchange system. The routing manager can include a network address translation layer. For example, each outside entity can be given particular IP addresses. The routing manager can transparently figure out to which gateway the traffic could be forwarded. The routing manager can additionally address challenges of routing based on geographic region. Traffic may be routed to one of a set of regional exchange systems depending on various factors.

The routing manager or an alternative system can enable virtualized IP settings to provide a level of abstraction between the IP address used by an outside entity and the actual IP of the computing resources.

The system can additionally include a configuration system (e.g., 112), which functions to enable provisioning, deprovisioning, and modifying of network exchange settings for an outside entity. An outside entity that wants to begin using a network exchange can enable such a feature through one of a variety of different interfaces.

One possible configuration interface can include a programmatic interface. More specifically, the programmatic interface is an application programming interface (API). The configuration interface is preferably a RESTful API but may alternatively be any suitable API such as SOAP or custom protocol. The RESTful API works according to an application layer request and response model. An application layer request and response model may use an HTTP-based protocol (HTTP or HTTPS), SPDY, or any suitable application layer protocol. Herein, HTTP may be used, but should not be interpreted as being limited to the HTTP protocol. HTTP requests (or any suitable request communication) to the communication platform preferably observe the principles of a RESTful design. RESTful is understood in this document to describe a Representational State Transfer architecture as is known in the art. The RESTful HTTP requests are preferably stateless, thus each message communicated contains all necessary information for processing the request and generating a response. The API service can include account exchange setting resources, which act resources that can in part define network exchange operation.

The configuration system can be a control portal user interface accessible through a website, an application, or other graphical user interface. An administrator of an account can preferably navigate to the control panel and select an option for adding and configuring one or more network exchanges used by the account as shown in FIG. 2.

The system can additionally include a metering and billing system. The metering subsystem of the preferred embodiment functions to monitor and log activity by an account through a network exchange. The metering and logging system operates in coordination with the system. The metering subsystem can track data activity including throughput, types of service traffic, and other properties of network exchange usage. The metering subsystem can be used in providing programmatic hooks (e.g., callback URI triggering, application execution, and the like), billing/crediting an associated entity (e.g., charging for services or controlling resource access), creation of an audit trail, and/or other suitable functionality.

A billing engine may operate independently of the metering subsystem, but may alternatively be integrated. A billing engine preferably calculates amount owed by a particular account/sub-account. The billing engine can additionally facilitate collecting and distributing of funds as appropriate. Such accounting may be used in billing or crediting an entity/account for metered usage, which functions to allow a sustainable media intelligence platform to be operated. In another variation, usage accountability can be used in limiting and balancing usage of a particular entity. As the platform is preferably multitenant, usage is preferably balanced across multiple entities. Rate limiting and action limits may be imposed at various times. Additionally, as use of a communication infrastructure is often accompanied with significant financial cost, fraudulent behavior by accounts or users of an account can be harmful to users of the platform and to the platform itself. Fraud detection can additionally be accounted for during usage of the platform.

As shown in FIG. 3, a method for configuring network exchange for a multitenant platform in a virtual private cloud can include setting configuration of an account S110, establishing network connection to at least one of a regional exchange systems S120, and routing traffic through the regional exchange system S130.

The method functions to enable a multitenant platform (e.g., 113) to offer network exchange functionality to a variety of entities using the multitenant platform. The method is particularly applicable to a multitenant platform as a service product that is hosted in an infrastructure as a service (IaaS) cloud computing product such as Amazon Web Services or other suitable hosting solutions. Current exchange solutions do not address the challenge of offering network exchange capabilities to multiple entities for a platform built in a virtual private cloud (VPC). The method can be used by entities that require or desire to have a more secure or reliable data link to the multi-tenant platform.

The processes of the method are preferably implemented by multiple entities. In one implementation, the method may be used repeatedly so that multiple end users of the multitenant platform establish independently managed network exchange integrations. For example, the method may be implemented in association with various customers of a telecommunication platform to establish voice or messaging communication through independent, secured network connections for each customer. In another implementation, the method may be used repeatedly so that multiple service providers of the multitenant platform. For example, the method may be implemented with various carrier networks used by a telecommunication platform. The carrier networks may not be end customers but rather resources used in facilitating performing operations on the multitenant platform. In a telecommunication platform, customers and service providers can preferably both use the network exchange.

The method is preferably implemented by a system substantially similar to the one described above (e.g., 100), but any suitable system may be used.

Block S110, which includes setting configuration of an account, functions to define settings for a network exchange of an account. The multitenant platform (e.g., 113) can have a plurality of different accounts. As described above, these accounts may be end user accounts, internal accounts (e.g., used for various outside vendors or service providers), and/or any suitable outside entity. The set of accounts can include a subset of accounts that use the network exchange functionality, but a second subset of accounts may not use the network exchange functionality. An account without a configured network exchange can provision or add a new network exchange option. Setting configuration of a new network exchange can include selecting the type of network exchange, setting account system settings, setting a region, and enrolling the account for the selected type of network exchange. As described above, a variety of network exchange interfaces may be used. The set of possible network exchange interfaces can include a VPN connection, a cross connect connection, and an MPLS connection. Additionally multiple different network exchange instances can be provisioned. Multiple network exchange instances for one account may provide regional performance enhancements, redundancies, and/or other benefits.

Setting configuration of a VPN can involve receiving or setting authentication credentials (e.g., username and password) and determining the IP address to be used. Cross connect may involve initializing a workflow for signing of a legal document to authorize use of the cross connect. Once confirmed, automated integration instructions can be issued. The integration issues may specify a port number and location to be used in a collocated environment to establish the cross connect integration. In one variation, a wire can be physically plugged in at the appropriate port in the regional exchange system. In another variation, the wires are prepopulated and a routing service configures the router to establish a cross connection between appropriate ports. MPLS may involve establishing a three-way agreement between appropriate entities if the outside entity is in the network. If the entity establishing the network exchange integration is not in the network, then a workflow can be initiated to onboard the entity into the network.

Setting configuration of an account may additionally include updating at least one previously provisioned network exchange instance. An authorized account could update the settings in any suitable manner.

Setting configuration of an account may additionally include deprovisioning a network exchange instance, which functions to deactivate, end, or suspend an accounts usage of a private and secured network integration.

Setting configuration can be performed through a programmatic interface or a user interface.

Block S120, which includes establishing network connection to at least one of a regional exchange systems (e.g., 120, 130), functions to connect the outside computing resources of the account holder (e.g., outside computing resources of Customer A, Customer B, Customer C) to those of the multitenant platform (e.g., 113). The network connection can be established over VPN, a cross connect connection, or an MPLS connection.

Block S130, which includes routing traffic through the regional exchange system, functions to receive and transmit data through the established regional exchange network. Routing traffic can include IP translation, which functions to translate between the public IP address used by a customer and the actual resource IP addressed of the hosts. Routing traffic can additionally include routing between the edge subnet and the private subnet. As mentioned multiple entities may have a network exchange connection. In some cases, a communication may be established through two or more network exchanges. For example, a phone call may be established from a customer's network exchange and that communication may have at least one leg connected to a carrier through a network exchange of the carrier.

Additionally, the method can include monitoring and responding to usage of the network connection. The usage, amount of traffic, types of services used and/or other activities may be tracked based on individual accounts. The accounts are preferably billed or credited for individual usage.

Systems

FIGS. 4A-C are schematic representations of systems 400 a-c in accordance with embodiments. In some embodiments, the systems 400 a-c include at least one virtual private cloud (VPC) system 401, and at least one regional exchange system (e.g., 420, 430).

In some embodiments, the VPC system 401 includes at least one virtual private cloud (e.g., VPC 410 a-c).

In some embodiments, the VPC system 401 (FIG. 4A) includes a VPC (e.g., 410 a, 410 b) for each regional exchange system (e.g., 420, 430). In some embodiments, the VPC system 401 (FIG. 4A) includes a VPC (e.g., 410 a, 410 b) for each regional exchange system (e.g., 420, 430), each regional exchange system is communicatively coupled one VPC (e.g., 410 a, 410 b), and each regional exchange system is communicatively coupled to a different VPC. In some embodiments, each VPC (e.g., 410 a, 410 b) that is communicatively coupled to a regional exchange system is not communicatively coupled to the Internet 460. In some embodiments, the VPC system 401 (FIG. 4A) includes a VPC (e.g., 411) that is communicatively coupled to the Internet 460.

In some embodiments, the VPC system 401 (FIG. 4B) includes a VPC (e.g., 410 c) for multiple regional exchange systems (e.g., 420, 430).

In some embodiments, the VPCs 410 a and 410 b of FIG. 4A, and the VPC 410 c of FIG. 4B each include a multi-tenant platform system (e.g., 413 a-c). In some embodiments, the VPCs 410 a-c each include a configuration system (e.g., 412 a-c). In some embodiments, the multi-tenant platform systems 413 a-c include at least one platform service (e.g., 414 a-c).

In some embodiments, the VPC 411 of FIG. 4A includes a multi-tenant platform system, as described herein. In some embodiments, the VPC 411 of FIG. 4A includes a configuration system, as described herein. In some embodiments, the VPC 411 is communicatively coupled to a PSTN network.

In some embodiments, as shown in system 400 c of FIG. 4C, the VPCs 410 a-b do not include a configuration system, the VPC 411 includes a configuration system 412 d (similar to configuration systems 412 a-c as described herein), the VPCs 410 a and 410 b are communicatively coupled to the configuration system 412 d of the VPC 411, and the configuration system 412 d of the VPC 411 is communicatively coupled to the Internet 460 .

In some embodiments, the VPC 410 a is communicatively coupled to the VPC 410 b.

In some embodiments, the systems 400 a and 400 b are similar to the system 100 of FIG. 1. In some embodiments, the system 400 c is similar to the system 100 of FIG. 1. In some embodiments, the regional exchange system 420 is similar to the regional exchange systems of FIG. 1. In some embodiments, the regional exchange system 430 is similar to the regional exchange systems of FIG. 1. In some embodiments, the configuration systems 412 a-d are similar to the configuration system of FIG. 1. In some embodiments, the multi-tenant platform systems 413 a-c are similar to the multi-tenant platform system of FIG. 1. In some embodiments, the VPCs 410 a-c are similar to the VPC 110 of FIG. 1. In some embodiments, the VPC 411 is similar to the VPC 110 of FIG. 1. In some embodiments, the VPC system 401 is similar to a system of a IaaS cloud environment as described herein for FIG. 1. In some embodiments, the VPC system 401 is similar to a system of a third party cloud solution provider as described herein for FIG. 1.

In some embodiments, the VPC system 401 is a VPC system of a IaaS (Infrastructure as a Service) provider.

In some embodiments, the VPC system 401 is an Amazon Web Services™ VPC system.

In some embodiments, the VPCs 410 a-c are managed by a first entity that is an account holder of a first VPC account of the VPC system 401, the VPCs 410 a-c are VPCs of the first VPC account, and the first entity is a PaaS (Platform as a Service) provider.

In some embodiments, the VPC 411 is managed by the first entity.

In some embodiments, each entity system that is communicatively coupled to a regional exchange system (e.g., 441-446) is associated with an account of the PaaS provider of the VPC that is communicatively coupled to the regional exchange system (e.g., 410 a-c). In some embodiments, each entity system that is communicatively coupled to a regional exchange system (e.g., 441-446) uses at least a first service (e.g., 414 a-c) of the respective multi-tenant platform system (e.g., 413 a-c) provided by the PaaS provider of the VPC (e.g., 410 a-c) that is communicatively coupled to the regional exchange system, and each entity system uses the first service (e.g., 414 a-c) by communicating with the multi-tenant platform system (e.g., 413 a-c) via a respective regional exchange system (e.g., 420, 430).

In some embodiments, the VPCs 410 a-c are managed by a first entity that is an account holder of a first VPC account of the VPC system 401, the VPCs 410 a-c are VPCs of the first VPC account, and the first entity is a SaaS (Software as a Service) provider. In some embodiments, each entity system that is communicatively coupled to a regional exchange system (e.g., 441-446) is associated with an account of the SaaS provider of the VPC that is communicatively coupled to the regional exchange system (e.g., 410 a-c). In some embodiments, each entity system that is communicatively coupled to a regional exchange system (e.g., 441-446) uses at least a first service provided by the SaaS provider of the VPC that is communicatively coupled to the regional exchange system (e.g., 410 a-c), and each entity system uses the first service by communicating with the VPC (that is communicatively coupled to the regional exchange system e.g., 410 a-c) via a respective regional exchange system (e.g., 420, 430).

In some embodiments, the multi-tenant platform systems 413 a-c are communicatively coupled to a respective configuration system 412 a-c. In some embodiments, a multi-tenant platform system (e.g. of the VPC 411) is communicatively coupled to the Internet. In some embodiments, the multi-tenant platform systems 413 a-c are communicatively coupled to at least one PSTN network (Public Switched Telephone Network).

In some embodiments, the multi-tenant platform systems are communicatively coupled to one regional exchange system (e.g., 420, 430). In some embodiments, the multi-tenant platform systems are communicatively coupled to one regional exchange system (e.g., 420, 430) via a private network connection. In some embodiments, the multi-tenant platform system 413 a is communicatively coupled to regional exchange system 420 via a private network connection. In some embodiments, the multi-tenant platform system 413 b is communicatively coupled regional exchange system 430 via a private network connection.

In some embodiments, the multi-tenant platform system 413 c is communicatively coupled to regional exchange system 420 via a private network connection. In some embodiments, the multi-tenant platform system 413 c is communicatively coupled regional exchange system 430 via a private network connection.

In some embodiments, the private network connection is a VLAN private network connection. In some embodiments, the private network connection is an 802.1Q VLAN private network connection. In some embodiments, the private network connection is an AWS (Amazon Web Services) Direct Connect private network connection.

In some embodiments, the regional exchange system 420 is communicatively coupled to at least one outside entity system (e.g., 441-446) via a private network exchange by using a secure connection interface (e.g., 421-423) of the regional exchange system 420. In some embodiments, the regional exchange system 420 is communicatively coupled to at least one customer outside entity system (e.g., 441-446) via a private network exchange. In some embodiments, the regional exchange system 420 is communicatively coupled to at least one service provider outside entity system (e.g., 441-446) via a private network exchange.

In some embodiments, the regional exchange system 430 is similar to the regional exchange system 420.

In some embodiments, the regional exchange system 430 is communicatively coupled to at least one outside entity system (e.g., 441-446) via a private network exchange by using a secure connection interface (e.g., 431-433) of the regional exchange system 430. In some embodiments, the regional exchange system 430 is communicatively coupled to at least one customer outside entity system (e.g., 441-446) via a private network exchange. In some embodiments, the regional exchange system 430 is communicatively coupled to at least one service provider outside entity system (e.g., 441-446) via a private network exchange.

In some embodiments, each regional exchange system (e.g., 420, 430) includes at least one secure connection interface (e.g., 421-423, 432-433). In some embodiments, each regional exchange system (e.g., 420, 430) includes a VPN secure connection interface (e.g., 421, 431), a cross connect secure connection interface (e.g., 422, 432), and an MPLS secure connection interface (e.g., 423, 433).

In some embodiments, each regional exchange system (e.g., 420, 430) is managed by a first entity that is an account holder of a first VPC account of the VPC system 401, the VPCs (e.g., 410 a-c) are VPCs of the first VPC account, and the first entity is a PaaS (Platform as a Service) provider. In some embodiments, each regional exchange system (e.g., 420, 430) is managed by a first entity that is an account holder of a first VPC account of the VPC system 401, the VPCs (e.g., 410 a-c) are VPCs of the first VPC account, and the first entity is a SaaS (Software as a Service) provider.

In some embodiments, each regional exchange system (e.g., 420, 430) is managed by an entity that is different from an entity that manages the VPC system 401. In some embodiments, each regional exchange system (e.g., 420, 430) is managed by a first entity that is an account holder of a VPC account of the VPC system 401, and the VPC system 401 is managed by a second entity that is different from the first entity. In some embodiments, the first entity is a PaaS (Platform as a Service) provider, and the second entity is a IaaS (Infrastructure as a Service) provider. In some embodiments, the first entity is a SaaS (Software as a Service) provider, and the second entity is a IaaS (Infrastructure as a Service) provider.

In some embodiments, each outside entity system (e.g., 441-446) is a router. In some embodiments, at least one outside entity system (e.g., 441-446) is a router. In some embodiments, each outside entity system (e.g., 441-446) is communicatively coupled to a PBX system of the respective entity. In some embodiments, at least one outside entity system (e.g., 441-446) is communicatively coupled to a PBX system of the respective entity. In some embodiments, each PBX system is communicatively coupled to at least one communication client device. In some embodiments, at least one PBX system is communicatively coupled to at least one communication client device.

In some embodiments, each hardware server of the multi-tenant platform systems 413 a-c is managed by the VPC system 401. In some embodiments, each hardware server of the configuration systems 412 a-d is managed by the VPC system 401. In some embodiments, the VPC system 401 is a hardware system. In some embodiments, the VPC system 401 of FIG. 4A includes at least one hardware server of the VPCs 410 a-b and at least one hardware server of a VPC (not shown in FIG. 4A) of an entity different from an entity of the VPCs 410 a-b. In some embodiments, the VPC system 401 of FIG. 4B includes at least one hardware server of the VPC 401 c and at least one hardware server of a VPC (not shown in FIG. 4B) of an entity different from an entity of the VPC 410 c.

In some embodiments, the platform services 414 a-c are communication services. In some embodiments, the platform services 414 a-c are real-time voice communication services. In some embodiments, the platform services 414 a-c are messaging communication services. In some embodiments, the platform services 414 a-c are SIP (Session Initiation Protocol) communication services that are constructed to communicate SIP data. In some embodiments, the platform services 414 a-c are message communication services that are constructed to communicate asynchronous message data. In some embodiments, the platform services 414 a-c are video communication services that are constructed to communicate video data. In some embodiments, the platform services 414 a-c are IP Client communication services that are constructed to communicate IP Client communication data. In some embodiments, the platform services 414 a-c are WebRTC (Web Real-Time Communication) communication services that are constructed to communicate WebRTC data.

In some embodiments, regional exchange system 420 is external to the VPC system 401 and the entity systems 441-446. In some embodiments, regional exchange system 430 is external to the VPC system 401 and the entity systems 441-446. In some embodiments, the entity systems 441-446 are external to the VPC system 401.

Methods

FIGS. 5A-D are flow diagram representations of methods in accordance with embodiments. In some embodiments, the method 500 is performed by the system 100 of FIG. 1. In some embodiments, the method 500 is performed by the system 400 a of FIG. 4A. In some embodiments, the method 500 is performed by the system 400 b of FIG. 4B. In some embodiments, the method 500 is performed by the system 400 c of FIG. 4C.

In some embodiments, the method 500 includes: setting configuration of a first account (process S510), establishing a first private network exchange between a first regional exchange system (e.g., one of 420 and 430) and a first outside entity system (e.g., on of 441-446) of the first account (process S520); and routing traffic through the regional exchange system (process S530). In some embodiments, setting configuration of a first account (process S510) includes: a virtual private cloud (VPC) system (e.g., 401) receiving first configuration for a first private network exchange for the first account of the VPC system (process S511), and the VPC system assigning the first regional exchange system (e.g., one of 420 and 430) to the first private network exchange based on the first configuration (process S512). In some embodiments, establishing a first private network exchange between a first regional exchange system and a first outside entity system of the first account (process S520) includes mapping an identifier of the first account to the first private network exchange (process S521). In some embodiments, routing traffic through the regional exchange system (process S530) includes routing communication data for the first account from a first service (e.g., 414 a-c) of the VPC system to the first outside entity system via the first private network exchange based on the mapping (process S531).

In some embodiments, the method 500 is similar to the method 300 of FIG. 3. In some embodiments, the process S510 is similar to the process S110 of FIG. 3. In some embodiments, the process S520 is similar to the process S120 of FIG. 3. In some embodiments, the process S530 is similar to the process S130 of FIG. 3.

In some embodiments, the first account is an account of a first multi-tenant platform system (e.g., 413 a-c) of a first VPC (e.g., 410 a-c) of the VPC system (e.g., 401), and the first service (e.g., 414 a-c) is a service of the first multi-tenant platform system. In some embodiments, the first VPC is a VPC of a PaaS provider. In some embodiments, the first VPC is a VPC of a SaaS provider. In some embodiments, an entity of the first account uses a service (e.g., 414 a-c) provided by the first multi-tenant platform system (e.g., 413 a-c). In some embodiments, an entity of the first multi-tenant platform system (e.g., 413 a-c) uses a service provided by the VPC system, and the VPC system and the multi-tenant platform system are managed by different entities.

In some embodiments, the VPC system receiving the first configuration (process S511) includes a configuration system (e.g., 412 a-c) of a first VPC (e.g., 410 a-c) of the VPC system receiving the first configuration. In some embodiments, the VPC system receiving the first configuration (process S511) includes a configuration system (e.g., 412 d) that is communicatively coupled to a first VPC (e.g., 410 a-c) of the VPC system receiving the first configuration. In some embodiments, the VPC system receiving the first configuration (process S511) includes a configuration system (e.g., 412 a-c) of a first VPC of the VPC system receiving the first configuration and storing the first configuration in the first VPC in association with the first account. In some embodiments, the VPC system receiving the first configuration (process S511) includes a configuration system (e.g., 412 d) communicatively coupled to a first VPC of the VPC system receiving the first configuration and storing the first configuration in association with the first account. In some embodiments, the VPC system receiving the first configuration (process S511) includes a multi-tenant platform system (e.g., 413 a-c) of a first VPC of the VPC system receiving the first configuration. In some embodiments, a VPC system receiving the first configuration (process S511) includes a multi-tenant platform system (e.g., 413 a-c) of a first VPC of the VPC system receiving the first configuration and storing the first configuration in the first VPC in association with the first account.

Private Network Exchange

In some embodiments, the first private network exchange is a layer 2 network exchange in accordance with a layer 2 network protocol.

Process S512: Assigning a Regional Exchange System

In some embodiments, the VPC system assigning the first regional exchange system to the first private network exchange (process S512) includes a configuration system (e.g., 412 a-c) of a first VPC of the VPC system assigning the first regional exchange system to the first private network exchange.

In some embodiments, the VPC system assigning the first regional exchange system to the first private network exchange (process S512) includes a configuration system (e.g., 412 d) communicatively coupled to a first VPC of the VPC system assigning the first regional exchange system to the first private network exchange.

In some embodiments, the VPC system assigning the first regional exchange system to the first private network exchange (process S512) includes a multi-tenant platform system (e.g., 413 a-c) of a first VPC of the VPC system assigning the first regional exchange system to the first private network exchange. In some embodiments, the VPC system assigning the first regional exchange system to the first private network exchange (process S512) includes a routing manager of a first VPC (e.g., 410 a-c) of the VPC system assigning the first regional exchange system to the first private network exchange.

In some embodiments, the VPC system assigning the first regional exchange system to the first private network exchange (process S512) includes: selecting the first regional exchange system from a plurality of regional exchange systems (e.g., 420, 430) based on the first configuration, and the plurality of regional exchange systems are external to the VPC system.

In some embodiments, the first configuration specifies selection of one of a plurality of private network exchange types (e.g., VPN, Cross Connet, MPLS), and the first regional exchange system is selected from a plurality of regional exchange systems (e.g., 420, 430) responsive to a determination that the first regional exchange system includes a secure connection interface (e.g., 421-423) for the private network exchange types specified by the first configuration. In some embodiments, the first private network exchange is a network exchange of the type specified by the first configuration.

In some embodiments, the first configuration specifies a bandwidth, and the first regional exchange system is selected from a plurality of regional exchange systems (e.g., 420, 430) responsive to a determination that the first regional exchange system can provide the bandwidth specified by the first configuration.

In some embodiments, the first configuration specifies a geographic location, and the first regional exchange system is selected from a plurality of regional exchange systems (e.g., 420, 430) responsive to a determination that the first regional exchange system is located in the geographic location specified by the first configuration.

Routing Communication Data

In some embodiments, a routing manager of a first VPC (e.g., 410 a-c) of the VPC system routes the communication data based on the mapping. In some embodiments, the first service routes the communication data based on the mapping. In some embodiments, the first regional exchange system routes the communication data based on the mapping.

Services

In some embodiments, the first service (e.g., 414 a-c) is a real-time voice communication service and the communication data is real-time voice communication data.

In some embodiments, the first service (e.g., 414 a-c) is a real-time voice communication service, and the communication data includes voice call data received by the VPC system from a PSTN device via a PSTN network. In some embodiments, the first account is associated with a phone number of a PSTN network, and communication data for the first account is communication data for the associated phone number.

In some embodiments, the first service (e.g., 414 a-c) is a SIP communication service and the communication data is SIP data. In some embodiments, the first account is associated with a SIP endpoint. In some embodiments, the first account is associated with a SIP endpoint, and communication data for the first account is communication data for the associated SIP endpoint.

In some embodiments, the first service (e.g., 414 a-c) is a WebRTC communication service and the communication data is WebRTC data. In some embodiments, the first account is associated with a WebRTC endpoint. In some embodiments, the first account is associated with a WebRTC endpoint, and communication data for the first account is communication data for the associated WebRTC endpoint.

In some embodiments, the first service (e.g., 414 a-c) is a messaging communication service and the communication data is messaging communication data.

In some embodiments, the first account is associated with a messaging endpoint.

In some embodiments, the VPC system 401 maps the identifier of the first account to the first private network exchange. In some embodiments, the configuration system (e.g., 412 a-d) maps the identifier of the first account to the first private network exchange. In some embodiments, the platform system (e.g., 413 a-c) maps the identifier of the first account to the first private network exchange. In some embodiments, a routing manager of the VPC (e.g., 410 a-c) maps the identifier of the first account to the first private network exchange.

Mapping the Account Identifier to the Private Network Exchange

In some embodiments, the first regional exchange system (e.g., 420, 430) maps the identifier of the first account to the first private network exchange. In some embodiments, the first regional exchange system receives the identifier of the first account and maps the received identifier to the first private network exchange. In some embodiments, the first regional exchange system receives the identifier of the first account from the VPC system (e.g., 401). In some embodiments, the first regional exchange system receives the identifier of the first account from a first VPC (e.g., 410 a-c) of the VPC system (e.g., 401). In some embodiments, a configuration system (e.g., 412 a-c) of a first VPC (e.g., 410 a-c) of the VPC system (e.g., 401) provides the first regional exchange system with the identifier of the first account. In some embodiments, a configuration system (e.g., 412 d) communicatively coupled to a first VPC (e.g., 410 a-c) of the VPC system (e.g., 401) provides the first regional exchange system with the identifier of the first account. In some embodiments, a routing manager of a first VPC (e.g., 410 a-c) of the VPC system (e.g., 401) provides the first regional exchange system with the identifier of the first account. In some embodiments, a multi-tenant platform system (e.g., 413 a-c) of a first VPC (e.g., 410 a-c) of the VPC system (e.g., 401) provides the first regional exchange system with the identifier of the first account. In some embodiments, the first regional exchange system receives the identifier of the first account from an outside system of the first account.

In some embodiments, the first reginal exchange system establishes the first private network exchange between the first regional exchange system and the first outside entity system. In some embodiments, the first reginal exchange system advertises a network route for the established first private network exchange to the VPC that is communicatively coupled to the first regional exchange system.

In some embodiments, the identifier of the first account is an IP address assigned to the first account for the first private network exchange.

In some embodiments, assigning the first regional exchange system (process S512) includes assigning an IP address within a subnet of the first regional exchange system to the first private network exchange. In some embodiments, assigning the first regional exchange system (process S512) includes assigning an IP address within a subnet of the first regional exchange system to the first private network exchange, and the identifier of the first account is the IP address assigned to the first private network exchange, and the first private network exchange is associated with the first account.

In some embodiments, assigning the first regional exchange system (process S512) includes a routing manager of a first VPC (e.g., 410 a-c) of the VPC system assigning an IP address within a subnet of the first regional exchange system to the first private network exchange, and the identifier of the first account is the IP address assigned to the first private network exchange, and the first private network exchange is associated with the first account.

In some embodiments, assigning the first regional exchange system (process S512) includes a configuration system (e.g., 413 a-c) of a first VPC (e.g., 410 a-c) of the VPC system assigning an IP address within a subnet of the first regional exchange system to the first private network exchange, and the identifier of the first account is the IP address assigned to the first private network exchange, and the first private network exchange is associated with the first account.

In some embodiments, the identifier for the first account is associated with the first account at the VPC system 401. In some embodiments, the identifier for the first account is associated with the first account at the configuration system (e.g., 412 a-d). In some embodiments, the identifier for the first account is associated with the first account at platform system (e.g., 413 a-c). In some embodiments, the identifier for the first account is associated with the first account at a routing manager of the VPC (e.g., 410 a-c).

In some embodiments, the identifier for the first account is associated with the first private network exchange at the first regional exchange system (e.g., 420, 430). In some embodiments, the first account is an account of a customer entity, and the first outside entity system (e.g., one of 441-446) is a customer system.

In some embodiments, the first account is an account of a service provider, and the first outside entity system (e.g., one of 441-446) is a service provider system. In some embodiments, the service provider system provides PSTN communication data that includes voice call data received by the service provider system from a PSTN device via a PSTN network, and the service provider system provides PSTN communication data to the VPC system via the first private network exchange. In some embodiments, the service provider system provides SIP communication data that includes voice call data received by the service provider system from a SIP device, and the service provider system provides SIP communication data to the VPC system via the first private network exchange. In some embodiments, the service provider system provides WebRTC communication data that includes voice call data received by the service provider system from a WebRTC device, and the service provider system provides WebRTC communication data to the VPC system via the first private network exchange.

In some embodiments, the service provider system provides asynchronous message communication data that includes message data received by the service provider system from a messaging client device, and the service provider system provides message communication data to the VPC system via the first private network exchange.

Sub-Accounts

In some embodiments, the first account is a first sub-account of a first entity, a second private network exchange is configured for a second sub-account of the first entity, and the second private network exchange is a network exchange for communication between the VPC system and a second outside entity system of the first entity.

Multi-Tenancy

In some embodiments, the first account is an account of a first VPC (e.g., 410 a-c) of the VPC system (e.g., 401). A second private network exchange is configured for a second account of the first VPC (e.g., 410 a-c), and the second account is associated with a second outside entity that uses a service of the first VPC. The second private network exchange is a network exchange for communication between the VPC system (e.g., 401) and a second outside entity system of the second entity.

Configuration

In some embodiments, the VPC system receives the first configuration via a public Internet connection.

In some embodiments, the first configuration is received from a system of an account holder of the first account via one of a programmatic interface and a graphical user interface, and the first configuration is stored in association with the first account at the VPC system. In some embodiments, the first configuration is received by a configuration system (e.g., 412 a-c), of a first VPC of the VPC system, from a system of an account holder of the first account via one of a programmatic interface and a graphical user interface, and the first configuration is stored in association with the first account at the first VPC. In some embodiments, the first configuration is received by a configuration system (e.g., 412 d), communicatively coupled to a first VPC of the VPC system, from a system of an account holder of the first account via one of a programmatic interface and a graphical user interface, and the first configuration is stored in association with the first account.

In some embodiments, a configuration system (e.g., 412 a-c), of a first VPC of the VPC system, receives the first configuration from a system of an account holder of the first account via a public Internet interface, and the configuration system receives second configuration for a second account from a system of an account holder of the second account via the public Internet interface.

In some embodiments, a configuration system (e.g., 412 d), communicatively coupled to a first VPC of the VPC system, receives the first configuration from a system of an account holder of the first account via a public Internet interface, and the configuration system receives second configuration for a second account from a system of an account holder of the second account via the public Internet interface.

Communication Between the VPC System and Regional Exchange Systems

In some embodiments, the VPC system and the first regional exchange system (e.g., 420) communicate via a private network connection. In some embodiments, the private network connection is a VLAN private network connection. In some embodiments, the private network connection is an 802.1Q VLAN private network connection. In some embodiments, the private network connection is an AWS (Amazon Web Services) Direct Connect private network connection.

Process S531: Routing Communication Data to the Outside Entity System

In some embodiments, routing communication data for the first account from a first service of the VPC system to the first outside entity system via the first private network exchange based on the mapping (process S531) includes: the VPC system providing the communication data to the first regional exchange system via the private network connection between the VPC system and the first regional exchange system, the first regional exchange system determining that the first private network connection is to be used for the communication data, and providing the received communication data to the first outside entity system via the determined first private network exchange. In some embodiments, the first regional exchange system determines that the first private network connection is to be used for the communication data based on the mapping performed at the process S521.

In some embodiments, the first regional exchange system determines that the first private network connection is to be used for the communication data based a destination IP address of the communication data. In some embodiments, the first regional exchange system determines that the first private network connection is to be used for the communication responsive to a determination that a destination IP address of the communication data is mapped to the first private network exchange.

In some embodiments, the first regional exchange system determines that the first private network connection is to be used for the communication data based a source IP address of the communication data. In some embodiments, the first regional exchange system determines that the first private network connection is to be used for the communication responsive to a determination that a source IP address of the communication data is mapped to the first private network exchange.

In some embodiments, the first regional exchange system determines that the first private network connection is to be used for the communication data based a destination communication endpoint identifier specified by the communication data.

In some embodiments, the first regional exchange system determines that the first private network connection is to be used for the communication responsive to a determination that a destination communication endpoint identifier of the communication data is mapped to the first private network exchange.

In some embodiments, the first regional exchange system determines that the first private network connection is to be used for the communication data based a source communication endpoint identifier specified by the communication data.

In some embodiments, the first regional exchange system determines that the first private network connection is to be used for the communication responsive to a determination that a source communication endpoint identifier of the communication data is mapped to the first private network exchange.

In some embodiments, the first regional exchange system uses an edge computing resource of the first regional exchange system to identify a destination communication endpoint identifier specified by the communication data, and the first regional exchange system determines that the first private network connection is to be used for the communication data based the identified destination communication endpoint identifier.

In some embodiments, the first regional exchange system uses an edge computing resource of the first regional exchange system to identify a source communication endpoint identifier specified by the communication data, and the first regional exchange system determines that the first private network connection is to be used for the communication data based the identified source communication endpoint identifier.

In some embodiments, the communication data is SIP data, the edge computing resource includes a SIP edge server, and the destination communication endpoint identifier is specified by a SIP “To” header of the SIP data.

In some embodiments, the communication data is SIP data, the edge computing resource includes a SIP edge server, and the source communication endpoint identifier is specified by a SIP “From” header of the SIP data.

In some embodiments, the communication data is WebRTC data, and the edge computing resource includes a WebRTC edge server.

In some embodiments, the communication data is WebRTC data, the edge computing resource includes a WebRTC edge server, and the source communication endpoint identifier is specified by a SIP “From” header of the WebRTC data.

In some embodiments, the communication data is WebRTC data, the edge computing resource includes a WebRTC edge server, and the destination communication endpoint identifier is specified by a SIP “To” header of the WebRTC data.

In some embodiments, the communication data is IP Client communication data, and the edge computing resource includes a IP Client communication server.

In some embodiments, the communication data is video data, and the edge computing resource includes a video streaming server.

In some embodiments, the communication data is asynchronous message data, and the edge computing resource includes a messaging server.

Authorization for Communication Via Private Network Exchange

In some embodiments, routing communication data for the first account from a first service (e.g., 414 a-c) of the VPC system to the first outside entity system via the first private network exchange based on the mapping (process S531) includes: the VPC system providing the communication data of the first service to the first regional exchange system responsive to a determination that communication to a destination endpoint identified by the communication data is authorized to receive the communication data via the first private network exchange.

In some embodiments, a configuration system (e.g., 412 a-c) of a first VPC of the VPC system provides the communication data of the first service to the first regional exchange system responsive to a determination that communication to a destination endpoint identified by the communication data is authorized to receive the communication data via the first private network exchange.

In some embodiments, a configuration system (e.g., 412 d) communicatively coupled to a first VPC of the VPC system provides the communication data of the first service to the first regional exchange system responsive to a determination that communication to a destination endpoint identified by the communication data is authorized to receive the communication data via the first private network exchange.

In some embodiments, a multi-tenant platform system (e.g., 413 a-c) of a first VPC of the VPC system provides the communication data of the first service to the first regional exchange system responsive to a determination that communication to a destination endpoint identified by the communication data is authorized to receive the communication data via the first private network exchange.

In some embodiments, routing communication data for the first account from a first service (e.g., 414 a-c) of the VPC system to the first outside entity system via the first private network exchange based on the mapping (process S531) includes: the VPC system providing the communication data of the first service to the first regional exchange system responsive to a determination that a source endpoint identified by the communication data is authorized to provide the communication data via the first private network exchange.

In some embodiments, a configuration system (e.g., 412 a-c) of a first VPC of the VPC system provides the communication data of the first service to the first regional exchange system responsive to a determination that a source endpoint identified by the communication data is authorized to provide the communication data via the first private network exchange.

In some embodiments, a configuration system (e.g., 412 d) communicatively coupled to a first VPC of the VPC system provides the communication data of the first service to the first regional exchange system responsive to a determination that a source endpoint identified by the communication data is authorized to provide the communication data via the first private network exchange.

In some embodiments, a multi-tenant platform system (e.g., 413 a-c) of a first VPC of the VPC system provides the communication data of the first service to the first regional exchange system responsive to a determination that a source endpoint identified by the communication data is authorized to provide the communication data via the first private network exchange.

In some embodiments, the VPC system identifies the destination endpoint by using the first service. In some embodiments, the VPC system identifies the source endpoint by using the first service.

In some embodiments, a configuration system (e.g., 412 a-c) of a first VPC of the VPC system identifies the destination endpoint by using the first service.

In some embodiments, a configuration system (e.g., 412 a-c) of a first VPC of the VPC system identifies the source endpoint by using the first service.

In some embodiments, a configuration system (e.g., 412 d) communicatively coupled to a first VPC of the VPC system identifies the destination endpoint by using the first service.

In some embodiments, a configuration system (e.g., 412 d) communicatively coupled to a first VPC of the VPC system identifies the source endpoint by using the first service.

In some embodiments, a multi-tenant platform system (e.g., 413 a-c) of a first VPC of the VPC system identifies the destination endpoint by using the first service.

In some embodiments, a multi-tenant platform system (e.g., 413 a-c) of a first VPC of the VPC system identifies the source endpoint by using the first service.

In some embodiments, the communication data is SIP data, the first service a SIP service, and the destination communication endpoint identifier is specified by a SIP “To” header of the SIP data.

In some embodiments, the communication data is SIP data, the first service a SIP service, and the source communication endpoint identifier is specified by a SIP “From” header of the SIP data.

In some embodiments, the communication data is WebRTC data, the first service a WebRTC service, and the destination communication endpoint identifier is specified by a SIP “To” header of the WebRTC data.

In some embodiments, the communication data is WebRTC data, the first service a WebRTC service, and the source communication endpoint identifier is specified by a SIP “From” header of the WebRTC data.

Information Identifying an Account

In some embodiments, communication data routed from the first outside entity system to the first service via the regional exchange system includes information identifying the first account. In some embodiments, the information identifying the first account is an IP address. In some embodiments, the information identifying the first account is a communication endpoint identifier.

Routing Communication Data from an Entity System to the VPC System

In some embodiments, routing traffic through the regional exchange system (process S530) includes: routing communication data for the first account from the first outside entity system to the first service of the VPC system via the first private network exchange by performing IP translation between a public IP address of the first service used by the first outside entity system and a private IP address of the first service used within the VPC system.

In some embodiments, a first VPC (e.g., 410 a-c) of the VPC system assigns a first private IP address of the first VPC to the first service, the first regional exchange system maps a first public IP address of the first regional exchange system to the first private IP address of the first service, assigns the first public IP address to the first account, and communication data for the first account received by the first regional exchange system from the first outside entity system specifies the first public IP address as a destination IP address. In some embodiments, the first regional exchange system performs IP address translation by replacing the first public IP address of the communication data received from the first outside entity system with the first private IP address, and providing the communication data with the first private IP address to the first service at the VPC system.

In some embodiments, communication data for the first account received by the first regional exchange system from the first service specifies the first private IP address as a source IP address, and the first regional exchange system performs IP address translation by replacing the first private IP address of the communication data received from the first service with the first public IP address, and providing the communication data with the first public IP address to the first outside entity system.

In some embodiments, the first VPC (e.g., 410 a-c) of the VPC system updates the first service by assigning a second private IP address of the first VPC to the first service, the first VPC provides the second private IP address of the updated first service to the first regional exchange system, and the first regional exchange system updates the mapping for the first public IP address of the first service with the second private IP address. In some embodiments, the first regional exchange system updates the mapping for the first public IP address by replacing the mapping of the first private IP address to the first public IP address with a mapping of the second private IP address to the first public IP address.

In some embodiments, a routing manager of the first VPC updates the first service and provides the second private IP address to the first regional exchange system. In some embodiments, a configuration system (e.g., 412 a-c) of the first VPC updates the first service and provides the second private IP address to the first regional exchange system. In some embodiments, a configuration system (e.g., 412 d) communicatively coupled to the first VPC updates the first service and provides the second private IP address to the first regional exchange system. In some embodiments, a multi-tenant platform system (e.g., 413 a-c) of the first VPC updates the first service and provides the second private IP address to the first regional exchange system.

In some embodiments, a multi-tenant platform system (e.g., 413 a-c) of the first VPC updates the first service and provides the second private IP address to the first regional exchange system. In some embodiments, an orchestration system of the first VPC updates the first service and provides the second private IP address to the first regional exchange system.

Voice Communication

In some embodiments, a first communication domain is associated with the first account and the first communication domain includes a set of communication endpoint identifiers.

In some embodiments, a multi-tenant platform system (e.g. 413 a-c) of a first VPC of the VPC system maps a communication domain (that includes a set of communication endpoints) of the first account to the first private network exchange.

In some embodiments, assigning the first regional exchange system (process S512) includes assigning a first IP address within a subnet of the first regional exchange system to the first private network exchange, and a multi-tenant platform system (e.g. 413 a-c) of a first VPC of the VPC system maps a communication domain of the first account to the first IP address assigned to the first private network exchange. In some embodiments, communication data received at the multi-tenant platform system that specifies a destination communication endpoint identifier that is included in the communication domain of the first account is provided to the first outside entity system via the first private network exchange.

SIP Communication

In some embodiments, the communication data is SIP data, the first service a SIP service, and a multi-tenant platform system (e.g., 413 a-c) of a first VPC of the VPC system maps a SIP domain of the first account to the first private network exchange.

In some embodiments, assigning the first regional exchange system (process S512) includes assigning a first IP address within a subnet of the first regional exchange system to the first private network exchange, the communication data is SIP data, the first service a SIP service, and a multi-tenant platform system (e.g., 413 a-c) of a first VPC of the VPC system maps a SIP domain of the first account to the first IP address assigned to the first private network exchange. In some embodiments, SIP communication data received at the multi-tenant platform system that specifies a destination SIP endpoint identifier that is included in the SIP domain of the first account is provided to the first outside entity system via the first private network exchange.

WebRTC Communication

In some embodiments, the communication data is WebRTC data, the first service a WebRTC service, and a multi-tenant platform system (e.g. 413 a-c) of a first VPC of the VPC system maps a SIP domain (for WebRTC communication) of the first account to the first private network exchange.

In some embodiments, assigning the first regional exchange system (process S512) includes assigning a first IP address within a subnet of the first regional exchange system to the first private network exchange, the communication data is WebRTC data, the first service a WebRTC service, and a multi-tenant platform system (e.g. 413) of a first VPC of the VPC system maps a SIP domain (for WebRTC communication) of the first account to the first IP address assigned to the first private network exchange. In some embodiments, WebRTC communication data received at the multi-tenant platform system that specifies a destination SIP endpoint identifier that is included in the SIP domain of the first account is provided to the first outside entity system via the first private network exchange.

Messaging Communication

In some embodiments, the communication data is asynchronous message data, the first service a messaging service, and a multi-tenant platform system (e.g. 413 a-c) of a first VPC of the VPC system maps a messaging domain (that includes messaging communication endpoint identifiers) of the first account to the first private network exchange.

In some embodiments, assigning the first regional exchange system (process S512) includes assigning a first IP address within a subnet of the first regional exchange system to the first private network exchange, the communication data is asynchronous message data, the first service a messaging service, and a multi-tenant platform system (e.g., 413 a-c) of a first VPC of the VPC system maps a messaging domain of the first account to the first IP address assigned to the first private network exchange. In some embodiments, asynchronous message communication data received at the multi-tenant platform system that specifies a destination messaging endpoint identifier that is included in the messaging domain of the first account is provided to the first outside entity system via the first private network exchange.

System Architecture: VPC System

FIG. 6 is a diagram depicting system architecture of a VPC system, according to embodiments. FIG. 6 is an architecture diagram of a VPC system (e.g., VPC system 401 of FIG. 4) according to an embodiment in which the VPC system is implemented by a server device. In some embodiments, the VPC system is implemented by a plurality of devices.

In some embodiments, the VPC system is implemented by a server device that includes machine-executable instructions (and related data) for the VPCs 410 a-b and 411.

In some embodiments, the VPC system is implemented by a plurality of devices, and the plurality of devices include machine-executable instructions (and related data) for the VPCs 410 a-b and 411.

In some embodiments, the VPC system is implemented by at least one server device that includes machine-executable instructions (and related data) for a plurality of VPCs including the VPCs 410 a-b and 411, and at least two of the plurality of VPCs are VPCs of different entities having different VPC accounts at the VPC system.

In some embodiments, the VPC system is an Amazon Web Services™ VPC system.

In some embodiments, the bus 601 interfaces with the processors 601A-601N, the main memory (e.g., a random access memory (RAM)) 622, a read only memory (ROM) 604, a processor-readable storage medium 605, and a network device 611. In some embodiments, the platform system includes at least one of a display device and a user input device.

In some embodiments, the processors 601A-601N may take many forms, such as ARM processors, X86 processors, and the like.

In some embodiments, the VPC system includes at least one of a central processing unit (processor) and a multi-processor unit (MPU).

In some embodiments, the processors 601A-601N and the main memory 622 form a processing unit 699. In some embodiments, the processing unit includes one or more processors communicatively coupled to one or more of a RAM, ROM, and machine-readable storage medium; the one or more processors of the processing unit receive instructions stored by the one or more of a RAM, ROM, and machine-readable storage medium via a bus; and the one or more processors execute the received instructions. In some embodiments, the processing unit is an ASIC (Application-Specific Integrated Circuit). In some embodiments, the processing unit is a SoC (System-on-Chip). In some embodiments, the processing unit includes one or more VPCs (e.g., 410 a-b, 411).

In some embodiments, the network device 611 provides one or more wired or wireless interfaces for exchanging data and commands between the VPC system and other devices, such as a regional exchange system (e.g., 420, 430), a device communicatively coupled to the VPC system via the Internet, and a device communicatively coupled to the VPC system via a PSTN network. Such wired and wireless interfaces include, for example, a universal serial bus (USB) interface, Bluetooth interface, an optical interface, Wi-Fi interface, Ethernet interface, near field communication (NFC) interface, and the like.

Machine-executable instructions in software programs (such as an operating system, application programs, and device drivers) are loaded into the memory 622 (of the processing unit 699) from the processor-readable storage medium 605, the ROM 604 or any other storage location. During execution of these software programs, the respective machine-executable instructions are accessed by at least one of processors 601A-601N (of the processing unit 699) via the bus 601, and then executed by at least one of processors 601A-601N. Data used by the software programs are also stored in the memory 622, and such data is accessed by at least one of processors 601A-601N during execution of the machine-executable instructions of the software programs. The processor-readable storage medium 605 is one of (or a combination of two or more of) a hard drive, a flash drive, a DVD, a CD, an optical disk, a floppy disk, a flash storage, a solid state drive, a ROM, an EEPROM, an electronic circuit, a semiconductor memory device, and the like. In some embodiments, the processor-readable storage medium 605 includes machine-executable instructions (and related data) for an operating system 612, software programs 613, device drivers 614, the VPCs 410 a-b and 411.

System Architecture: Regional Exchange System

FIG. 7 is a diagram depicting system architecture of a regional exchange system, according to embodiments. FIG. 7 is an architecture diagram of a regional exchange system (e.g., regional exchange system 420 of FIGS. 4A-C) according to an embodiment in which the regional exchange system is implemented by a server device. In some embodiments, the regional exchange system is implemented by a plurality of devices.

In some embodiments, the regional exchange system is implemented by a server device that includes machine-executable instructions (and related data) for the VPN interface 421, the cross connect interface 422, and the MPLS interface 423.

In some embodiments, the regional exchange system is implemented by a plurality of devices, and the plurality of devices include machine-executable instructions (and related data) for the VPN interface 421, the cross connect interface 422, and the MPLS interface 423.

The bus 701 interfaces with the processors 701A-701N, the main memory (e.g., a random access memory (RAM)) 722, a read only memory (ROM) 704, a processor-readable storage medium 705, and a network device 711. In some embodiments, the regional exchange system includes at least one of a display device and a user input device.

The processors 701A-701N may take many forms, such as ARM processors, X86 processors, and the like.

In some embodiments, the regional exchange system includes at least one of a central processing unit (processor) and a multi-processor unit (MPU).

The processors 701A-701N and the main memory 722 form a processing unit 799. In some embodiments, the processing unit includes one or more processors communicatively coupled to one or more of a RAM, ROM, and machine-readable storage medium; the one or more processors of the processing unit receive instructions stored by the one or more of a RAM, ROM, and machine-readable storage medium via a bus; and the one or more processors execute the received instructions. In some embodiments, the processing unit is an ASIC (Application-Specific Integrated Circuit). In some embodiments, the processing unit is a SoC (System-on-Chip). In some embodiments, the processing unit includes one or more of a VPN interface (e.g., 421), a cross connect interface (e.g., 422), and a MPLS interface (e.g., 423).

The network device 711 provides one or more wired or wireless interfaces for exchanging data and commands between the regional exchange system and other devices, such as a VPC system (e.g., 401 of FIG. 4) and an entity system (e.g., 441-446 of FIG. 4). Such wired and wireless interfaces include, for example, a universal serial bus (USB) interface, Bluetooth interface, an optical interface, Wi-Fi interface, Ethernet interface, near field communication (NFC) interface, and the like.

Machine-executable instructions in software programs (such as an operating system, application programs, and device drivers) are loaded into the memory 722 (of the processing unit 799) from the processor-readable storage medium 705, the ROM 704 or any other storage location. During execution of these software programs, the respective machine-executable instructions are accessed by at least one of processors 701A-701N (of the processing unit 799) via the bus 701, and then executed by at least one of processors 701A-701N. Data used by the software programs are also stored in the memory 722, and such data is accessed by at least one of processors 701A-701N during execution of the machine-executable instructions of the software programs. The processor-readable storage medium 705 is one of (or a combination of two or more of) a hard drive, a flash drive, a DVD, a CD, an optical disk, a floppy disk, a flash storage, a solid state drive, a ROM, an EEPROM, an electronic circuit, a semiconductor memory device, and the like. In some embodiments, the processor-readable storage medium 705 includes machine-executable instructions (and related data) for an operating system 712, software programs 713, device drivers 714, the VPC interface 421, the cross connect interface 422, and the MPLS interface 423.

Machines

The systems and methods of the preferred embodiments and variations thereof can be embodied and/or implemented at least in part as a machine configured to receive a computer-readable medium storing computer-readable instructions. The instructions are preferably executed by computer-executable components. The computer-readable medium can be stored on any suitable computer-readable media such as RAMs, ROMs, flash memory, EEPROMs, optical devices (CD or DVD), hard drives, floppy drives, or any suitable device. The computer-executable component is preferably a general or application specific processor, but any suitable dedicated hardware or hardware/firmware combination device can alternatively or additionally execute the instructions.

CONCLUSION

As a person skilled in the art will recognize from the previous detailed description and from the figures and claims, modifications and changes can be made to the preferred embodiments without departing from the scope of this invention defined in the following claims. 

What is claimed is:
 1. A method comprising: setting configuration of a first account comprising: a virtual private cloud (VPC) system receiving first configuration for a first private network exchange for the first account of the VPC system; and the VPC system assigning a first regional exchange system to the first private network exchange based on the first configuration; establishing the first private network exchange between the first regional exchange system and a first outside entity system of the first account comprising: mapping an identifier of the first account to the first private network exchange; routing traffic through the regional exchange system comprising: routing real-time voice communication data for the first account from a first real-time voice communication service of the VPC system to the first outside entity system via the first private network exchange based on the mapping.
 2. The method of claim 1, wherein the VPC system receives the first configuration via a public Internet connection, and wherein the first account is an account of a first multi-tenant platform system of a first VPC of the VPC system, and wherein the first service is a service of the first multi-tenant platform system.
 3. The method of claim 1, wherein assigning the first regional exchange comprises assigning an IP address within a subnet of the first regional exchange system to the first private network exchange.
 4. The method of claim 1, wherein the first regional exchange system is communicatively coupled to the VPC system via a private network connection.
 5. The method of claim 1, wherein the first configuration specifies a type of a plurality of types of private network exchanges, and the first private network exchange is of the specified type.
 6. The method of claim 1, wherein the first regional exchange system maps the identifier of the first account to the first private network exchange.
 7. The method of claim 1, wherein the identifier of the first account is an IP address assigned to the first account for the first private network exchange.
 8. The method of claim 1, wherein the identifier for the first account is associated with the first account at the VPC system, and wherein the identifier for the first account is associated with the first private network exchange at the first regional exchange system.
 9. The method of claim 1, wherein the first account is an account of a customer entity, and wherein the first outside entity system is a customer system.
 10. The method of claim 1, wherein the first account is an account of a service provider, and wherein the first outside entity system is a service provider system.
 11. The method of claim 1, wherein routing traffic through the regional exchange system further comprises: routing communication data for the first account from the first outside entity system to the first service of the VPC system via the first private network exchange by performing IP translation between a public IP address of the first service used by the first outside entity system and a private IP address of the first service used within the VPC system.
 12. The method of claim 1, wherein communication data routed from the first outside entity system to the first service via the regional exchange system includes information identifying the first account, wherein the information identifying the first account includes an IP address assigned to the first account by the VPC system.
 13. The method of claim 1, wherein mapping an identifier of the first account to the first private network exchange comprises: the first regional exchange system receiving the identifier and mapping the received identifier of the first account to the first private network exchange.
 14. The method of claim 13, wherein the first regional exchange system receives the identifier from the VPC system.
 15. The method of claim 13, wherein the first regional exchange system receives the identifier from an outside system of the first account.
 16. The method of claim 1, wherein the first regional exchange system includes interfaces for a plurality of types of private network exchange connections.
 17. The method of claim 1, wherein routing communication data for the first account from a first service of the VPC system to the first outside entity system via the first private network exchange based on the mapping comprises: the VPC system providing the communication data of the first service to the first regional exchange system responsive to a determination that a destination endpoint identified by the communication data is authorized to receive the communication data via the first private network exchange.
 18. The method of claim 1, wherein routing communication data for the first account from a first service of the VPC system to the first outside entity system via the first private network exchange based on the mapping comprises: the VPC system providing the communication data of the first service to the first regional exchange system responsive to a determination that a source endpoint identified by the communication data is authorized to provide the communication data via the first private network exchange.
 19. A method comprising: setting configuration of a first account comprising: a virtual private cloud (VPC) system receiving first configuration for a first private network exchange for the first account of the VPC system; and the VPC system assigning a first regional exchange system to the first private network exchange based on the first configuration; establishing the first private network exchange between the first regional exchange system and a first outside entity system of the first account comprising: mapping an identifier of the first account to the first private network exchange; routing traffic through the regional exchange system comprising: routing communication data for the first account from a first service of the VPC system to the first outside entity system via the first private network exchange based on the mapping.
 20. A method comprising: setting configuration of a first account comprising: a virtual private cloud (VPC) system receiving first configuration for a first private network exchange for the first account of the VPC system; and the VPC system assigning a first regional exchange system to the first private network exchange based on the first configuration; establishing the first private network exchange between the first regional exchange system and a first outside entity system of the first account comprising: mapping an identifier of the first account to the first private network exchange; routing traffic through the regional exchange system comprising: routing messaging communication data for the first account from a first messaging communication service of the VPC system to the first outside entity system via the first private network exchange based on the mapping. 